component of the LLLLAAAANNNNGGGG environment variable, or the
value of XXXXmmmmFFFFAAAALLLLLLLLBBBBAAAACCCCKKKK____CCCCHHHHAAAARRRRSSSSEEEETTTT if LLLLAAAANNNNGGGG is not set or
has no codeset component. The value of
XXXXmmmmFFFFAAAALLLLLLLLBBBBAAAACCCCKKKK____CCCCHHHHAAAARRRRSSSSEEEETTTT is defined by UIL supplier, but
is usually ISO8859-1 (equivalent to ISO_LATIN1).
Use of this clause turns off all localized string
literal processing turned on by the compiler flag
----ssss or the UUUUiiiillll____ccccoooommmmmmmmaaaannnndddd____ttttyyyyppppeeee ddddaaaattttaaaa ssssttttrrrruuuuccccttttuuuurrrreeee eeeelllleeeemmmmeeeennnntttt
You can later use these names in the UIL module as either
the value of an argument to a widget or the tag value to a
callback procedure. At run time, you use the MRM functions
MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessss and MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessssIIIInnnnHHHHiiiieeeerrrraaaarrrrcccchhhhyyyy to bind the
identifier name with the data (or, in the case of callbacks,
with the address of the data) associated with the
identifier.
Each UIL module has a single name space; therefore, you
cannot use a name you used for a value, object, or procedure
as an identifier name in the same module.
The UIL compiler does not do any type checking on the use of
identifiers in a UIL module. Unlike a UIL value, an
identifier does not have a UIL type associated with it.
Regardless of what particular type a widget argument or
callback procedure tag is defined to be, you can use an